Data storage system

ABSTRACT

The disclosed embodiments include data storage systems and methods to store data. In one embodiment, a computer-implemented method for storing data is disclosed. The method includes receiving a data value of a dataset. The method also includes assigning a plurality of keys of a key space to a plurality of data values of the dataset. The method further includes determining whether to readjust storage space of at least one partition of a plurality of partitions based on data values stored on the plurality of partitions. In response to a determination to readjust the at least one partition, the method further includes dynamically re-mapping the key space to readjust a number of keys of the plurality of keys that are assigned to data values stored on the plurality of partitions based on a number of data values that are stored on the plurality of partitions.

CLAIM OF PRIORITY

This application is a continuation application of co-pending U.S.Non-Provisional application Ser. No. 15/148,742 filed on May 6, 2016,entitled “Data Storage System,” the disclosures of which areincorporated by referenced herein in their entirety.

BACKGROUND

The present disclosure relates generally to data storage systems andmethods to store data.

External data sources often transmit various data values belonging toone or more datasets to one or more data storage systems for storage andfor re-transmission of the data values. Data storage systems ofteninclude or are communicatively connected to data storage mediums forstoring internal data as well as data obtained from one or more externaldata sources. The data storage mediums may have one or more data storagecomponents such as read-only memory (ROM), random access memory (RAM),flash memory, magnetic hard drives, solid state hard drives, CD-ROMdrives, DVD drives, floppy disk drives, as well as other types of datastorage components.

A data storage medium may be configured to store different types of datareceived by a data storage system. In that regard, each type of data ofa dataset may be allocated a section (partition) of the data storagemedium. The data storage system typically does not predetermine whichdata values of the dataset are transmitted by the external data sourcesuntil receipt of the data values. Further, the data storage systemtypically receives different types of data at different rates. Overtime, certain partitions of the storage medium may be saturated withdata values while other partitions of the storage medium may beunder-utilized or may not contain any data value. One conventionalsolution is to augment the storage medium to have enough storage tostore every data value of the dataset. However, since the data storagesystem may likely never receive some data values of the dataset, suchsolution is not only cost prohibitive, but also inefficiently utilizesavailable storage space of the data storage medium.

BRIEF SUMMARY

The disclosed embodiments provide systems and methods for storing datavalues. In accordance with one embodiment, a data storage system isprovided. The storage medium includes a plurality of partitions forstoring data values of a dataset. The data storage system also includesa system manager operable to receive, over a network, a data value ofthe dataset from an external source communicatively connected to thesystem manager, the dataset having a plurality of data subsets. Thesystem manager is also operable to assign a plurality of data subsets ofthe dataset to the plurality of partitions. The data storage systemfurther includes a key manager operable to assign a key of a key spaceto each data value of the dataset. The data storage system furtherincludes at least one data manager. Each data manager is assigned a datasubset of the plurality of data subsets. Each data manager is operableto store a set of keys on a partition the data subset is assigned to,where the set of keys has one or more keys assigned to data valuesbelonging to the data subset. Each data manager is further operable toprovide an indication of whether the data value belongs to the datasubset based on whether a key assigned to the data value is stored onthe partition, obtain the data value of the data subset from the systemmanager, and store the obtained data value on the partition. The datastorage system further includes an allocation manager operable todetermine whether to readjust a storage space of at least one partitionof the plurality of partitions. The allocation manager is furtheroperable to dynamically readjust the at least one partition based on atleast one of a frequency data values of the dataset are stored on the atleast one partition and a storage capacity of the at least onepartition.

In accordance with another illustrative embodiment a method for storingdata is provided. The method includes receiving, over a network, a datavalue of a dataset having a plurality of granules (data subsets), eachsubset having a plurality of data values sharing a common parameter. Themethod also includes determining, based on a parameter of the datavalue, a data subset of the plurality of data subsets sharing theparameter. The method further includes assigning a set of keys of a keyspace to each data subset of the plurality of data subsets. The methodfurther includes assigning each data subset of the dataset to a datamanager of at least one data manager. The method further includesstoring the received data value on a first partition of a plurality ofpartitions of a storage medium. The method further includes updating thefirst partition to indicate that the received data value is stored onthe first partition. The method further includes determining whether toreadjust a storage space of the first partition based on data valuesstored on the first partition.

In accordance with another illustrative embodiment, a machine-readablemedium including instructions stored therein, which when executed by oneor more processors, causes the one or more processors to performoperations to store data is provided. The instructions includeinstructions for receiving, over a network, a data value of a datasethaving a plurality of data subsets, each subset having a plurality ofdata values sharing a common parameter. The instructions also includeinstructions for determining, based on a parameter of the data value, adata subset of the plurality of data subsets sharing the parameter. Theinstructions further include instructions for assigning a set of keys ofa key space to each data subset of the plurality of data subsets. Theinstructions further include instructions for assigning, each datasubset of the dataset to a partition of a plurality of partitions of astorage medium, each partition of the plurality of partitions beingallocated to a data manager of at least one data manager. Theinstructions further include instructions for allocating the receiveddata value to a first partition of the plurality of partitions, thefirst partition being allocated to a first data manager of the at leastone data manager. The instructions further include instructions forstoring the received data value on the first partition of a plurality ofpartitions of a storage medium. The instructions further includeinstructions for updating the first partition to indicate that thereceived data value is stored on the first partition. The instructionsfurther include instructions for periodically determining whether toreadjust a storage space of the first partition based on data valuesstored on the first partition.

Additional details of the disclosed embodiments are provided below inthe detailed description and corresponding drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

Illustrative embodiments of the present invention are described indetail below with reference to the attached drawing Figures, which areincorporated by reference herein, and wherein:

FIG. 1 is a network environment for storing data in accordance with oneembodiment.

FIG. 2 is a schematic view of the data storage system of FIG. 1 inaccordance with one embodiment.

FIG. 3 is a schematic view of a data manager and a partition of astorage medium component of the data storage system in accordance withone embodiment.

FIG. 4 is a schematic view of an allocation manager of FIG. 2 assignedto three data managers and three partitions in accordance with oneembodiment.

FIG. 5A is a schematic view of an initial state of the partitions ofFIG. 4 and a key space containing three sets of keys mapped to datavalues stored on the partitions in accordance with one embodiment.

FIG. 5B is a schematic view of the partitions and key space of FIG. 5Aat time T after the initial state in accordance with one embodiment.

FIG. 6 is a schematic view of the data storage system of FIG. 1 havingmultiple layers of data managers in accordance with one embodiment.

FIG. 7 is a schematic view of the data storage system of FIG. 1 havingmultiple layers of data managers in accordance with another embodiment.

The illustrated figures are only exemplary and are not intended toassert or imply any limitation with regard to the environment,architecture, design, or process in which different embodiments may beimplemented.

DETAILED DESCRIPTION

FIG. 1 is a network environment 100 for storing data in accordance withone embodiment. The network environment 100 includes a data storagesystem 102. communicatively connected to external data sources 108, 110,112, and 114 via a network 106 and operable to receive data values fromthe external data sources 108, 110, 112, and 114 over the network 106.

The data storage system 102 includes one or more electronic devices orhardware/software component thereof, operable to receive data valuesfrom the data sources 108, 110, 112, and 114, store the received datavalues on a machine or computer readable medium (storage medium) 104,and dynamically readjust partitions of the storage medium 104 based onthe received data values and/or a frequency of the received data values.Examples of electronic devices include server computers, desktopcomputers, laptop computers, tablet computers, smartphones, PDAs, andsimilar electronic devices.

The storage medium 104 may be formed from data storage components suchas, but not limited to, ROM, RAM, flash memory, magnetic hard drives,solid state hard drives, CD-ROM drives, DVD drives, floppy disk (hives,as well as other types of data storage components and devices. In someembodiments, the storage medium 104 includes multiple data storagedevices. In further embodiments, the multiple data storage devices maybe physically stored at different locations. The storage medium 104includes a plurality of partitions for storing data values obtained fromthe external data sources 108, 110, 112, and 114. In some embodiments,the storage medium 104 of the data storage system 102 also includesinstructions for operating the data storage system 102.

The data storage system 102 includes a system manager component (systemmanager), at least one data manager component (data manager), and anallocation manager component (allocation manager). The system managerreceives data values transmitted by one or more of the external datasources 108, 110, 112, and 114. The data values belong to a datasethaving multiple data subsets. The system manager assigns the datasubsets to one or more partitions of the storage medium 104. Further,one or more data managers store the received data values on the one ormore partitions of the storage medium 104. Additional descriptions ofthe system manager, the data manager, as well as how data values areassigned and stored on the storage medium 104 are provided in thesubsequent paragraphs and are illustrated in FIGS. 2-7.

The allocation manager determines if the some of the partitions aresaturated. As defined herein, a partition is “saturated” if theallocation manager may allocate additional storage space to thepartition. In some embodiments, the partition is saturated if a firstthreshold percentage of the partition contains data values. In otherembodiments, the partition is saturated if a first threshold number ofdata values are stored on the partition. In some embodiments, theallocation manager also predicts when the partition may become saturatedbased on a frequency of data values received by the data storage system102 within an operational duration or based on a frequency of datavalues stored on the partition within the operational duration. In oneof such embodiments, the partition may become saturated if the number ofnew data values stored on the partition within an operational durationexceeds a second numerical threshold. In another one of suchembodiments, the partition may become saturated if the combined size ofdata values stored on the partition within the operational durationexceeds a first threshold size. In a further one of such embodiments,the partition may become saturated if a second threshold percentage ofthe partition is filled with new data values within the operationalduration.

The allocation manager also determines if some of the partitions areunder-utilized. As defined herein, a partition is “under-utilized” ifthe allocation manager may allocate some of the partition's unusedstorage space to another partition. In some embodiments, the partitionis under-utilized if a third threshold percentage of the partition doesnot contain data values. In further embodiments, the partition isunder-utilized if data values stored on the partition have a combinedsize that is less than a second threshold size.

In some embodiments, the allocation manager determines whether thepartition is under-utilized, saturated, may become under-utilized, ormay become saturated not only based on the number of data values storedon the partition or the frequency of data values stored on thepartition, but also based on the number of data values stored on otherpartitions of the storage medium 104 as well as the frequency at whichdata values are stored on the other partitions of the storage medium104. In one of such embodiments, the partition is saturated if thenumber of data values stored on the partition is a fourth thresholdpercentage greater than the average number of data values stored on thepartitions of the storage medium 104. In another one of suchembodiments, the partition is under-utilized if the number of datavalues stored on the partition is a fifth threshold percentage less thanthe average number of data values stored on the partitions of thestorage medium 104. In such embodiments, the determination of whetherthe partition is saturated, under-utilized, may become saturated or maybecome under-utilized dynamically changes as different data values arereceived by the data storage system 102.

The allocation manager dynamically readjusts a saturated partition byallocating unused storage space from one or more under-utilizedpartitions to the saturated partitions. Additional descriptions of theallocation manager as well as other components of the data storagesystem 102 are provided in the following paragraphs and are illustratedin at least FIGS. 2-7.

The external data sources 108, 110, 112, and 114 include any hardwareand/or software running on an electronic device operable to provide datavalues over the network 106 to the data storage system 102. Examples ofelectronic devices include server computers, desktop computers, laptopcomputers, tablet computers, smartphones, PDAs, and similar electronicdevices.

The network 106 can include, for example, any one or more of a cellularnetwork, a satellite network, a personal area network (PAN), a localarea network (LAN), a wide area network (WAN), a broadband network(BBN), the Internet, and the like. Further, the network 106 can include,but is not limited to, any one or more of the following networktopologies, including a bus network, a star network, a ring network, amesh network, a star-bus network, tree or hierarchical network, orsimilar network architecture. In some embodiments, the network 106includes a wired or wireless networking device (not shown) configured tofacilitate communication between the data storage system 102 and theexternal data sources 108, 110, 112, and 114. Examples of the networkingdevice include, but are not limited to, wired and wireless routers,wired and wireless modems, access points, as well as other types ofsuitable networking devices described herein. Although FIG. 1illustrates a single data storage system 102 communicatively connectedto the external data sources 108, 110, 112, and 114 via the network 106,additional data storage systems (not shown) and additional externalsources (not shown) may also be communicatively connected to the datastorage system 102 via the network 106 and operable to provide datavalues to the data storage system 102 via the network 106.

FIG. 2 is a schematic view of the data storage system 102 of FIG. 1 inaccordance with one embodiment. The data storage system 102 includes asystem manager 202, a key manager 203, an allocation manager 204, first,second and third data managers 206A-206C, and first, second, and thirdpartitions 208A-208C of the storage medium 104.

The system manager 202 receives data values of a dataset from theexternal sources 108, 110, 112, and 114. The dataset includes allpossible data values of a collection of data. Examples of datasetsinclude, but are not limited to all possible interact protocoladdresses, credit card numbers, financial security transaction numbers,usernames having a finite storage space, existing telephone numbers,postal codes, or any other collections of data that may be transmittedover the network 106. The key manager 203 maps each data value of thedataset to a key on a key space, where each key may be used to identifya corresponding data value, determine whether the corresponding datavalue is stored on the storage medium 104, and identify the data managermanaging the corresponding data value. For example, if a datasetcontains sixteen different data values, the key manager 203 assigns 16different keys of the keyset to the sixteen different data values of thedataset. Although FIG. 2 illustrates the system manager 202 and the keymanager 203 as separate components, the key manager 203 may also form asubcomponent of the system manager 202.

The dataset is divided into multiple data subsets based on parameters ofthe data values of the dataset. For example, a dataset of internetprotocol addresses may be divided into subsets containing governmentbased internet protocol addresses, private network internet addresses,multicast internet protocol addresses, or other categories of internetprotocol addresses based on the attributes of the internet protocoladdresses. Further, a dataset of usernames may be divided into datasubsets containing usernames beginning with a letter, usernamesbeginning with a number, and usernames beginning with a specialcharacter. In some embodiments, the system manager 202 provides thereceived data values to a data analyzer 205 to determine, based on atleast one parameter of the data value, a data subset that shares the atleast one parameter. Examples of data analyzers 205 include, but are notlimited to deep belief networks, auto encoders, packet sniffers, orsimilar components operable to analyze data values to determinecharacteristics or parameters of the data values. Additionaldescriptions of the data analyzer 205 are provided in the subsequentparagraphs. In some embodiments, the data analyzer 205 forms asubcomponent of the system manager 202. In other embodiments, the dataanalyzer 205 and the system manager 202 are separate components of thedata storage system 102.

The data analyzer 205 divides the dataset into a first data subset, asecond data subset, and a third data subset. Moreover, the systemmanager 202 assigns each of the first data manager 206A, the second datamanager 206B, and the third data manager 206C to manage the first datasubset, the second data subset, and the third data subset, respectively,and assigns the first data subset, the second data subset, and the thirddata subset to the first partition 208A, the second partition 208B, andthe third partition 208C of the storage medium 104, respectively.

The first data manager 206A is operable to store data values of thefirst data subset and keys assigned to the data values of the first datasubset on the first partition 208A. Similarly, the second and third datamanagers 206B and 206C are operable to store data values of the secondand third data subsets and keys assigned to the data values of thesecond data subset and the third data subset on the second and thirdpartitions 208B and 208C, respectively. In other embodiments, thedataset includes a different number of data subsets, where each datasetis managed by a data manager and is assigned to a partition of thestorage medium 104.

Each of the first, second, and third data managers 206A-206C maydetermine whether a data value received by the system manager 202belongs to a data subset managed by the respective data manager 206A,206B, or 206C. In some embodiments, each of the first, second, and thirddata managers 206A-206C calculates a probability that a key assigned tothe data value is stored on the first, second, or third partition 208A,208B, or 208C, respectively. Further, each of the first, second, andthird data managers 206A-206C also provides an indication of whether thedata value is managed by the respective data manager 206A, 206B, or206C. In one of such embodiments, each of the first, second, and thirddata managers 206A-206C then provides an indication of the calculatedprobability that a key assigned to the data value is stored on thefirst, second, or third partition 208A, 208B, or 208C, respectively. Inanother one of such embodiments, each of the first, second, and thirddata managers 206A-206C transmits an indication that the data valuebelongs to or does not belong to the data subset managed by therespective data manager 206A, 206B, or 206C. In other embodiments, theforegoing process is periodically performed by one or more of the first,second, and third data managers 206A, 206B, or 206C.

Over time, the data storage system 102 may receive more data valuesbelonging to one data subset of the dataset relative to other datasubsets of the dataset. As such, partitions 208A-208C may store unevenamounts of data values, and one of the partitions 208A, 208B, or 208Cmay become saturated, while another one of the partitions 208A, 208B, or208C may become under-utilized. The allocation manager 204 determineswhether to readjust the storage space of the partitions 208A-208C tomake better use of available storage space of one or more under-utilizedpartitions of the storage medium 104 by providing the available storagespace to one or more saturated partitions of the storage medium 104.

The allocation manager 204 then dynamically readjusts the partitions208A-208C to provide unused storage space of an under-utilized partitionto a saturated partition. In some embodiments, the allocation manager204 periodically determines how frequently data values of the datasetare stored on the partitions 208A-208C. In one of such embodiments, theallocation manager 204 determines the frequencies at which data valuesare stored on the first, second, and third partitions 208A-208C,respectively. As stated herein, the allocation manager 204 may predictwhen the partitions 208A-208C will become saturated based on frequenciesat which data values are stored on the respective partitions 208A-208Cwithin an operational duration. In one example embodiment, theallocation manager 204 increases the storage space of a partition 208A,208B, or 208C if the allocation manager 204 predicts that the respectivepartition 208A, 208B, or 208C will become saturated within a firstthreshold operational duration. Alternatively, the allocation manager204 decreases the storage space of a partition 208A, 208B, or 208C ifthe allocation manager 204 predicts that the respective partition 208A,208B, or 208C will not become saturated within a second thresholdoperational duration. In another one of such embodiments, the allocationmanager 204 predicts whether to increase or decrease the storage spaceof a partition 208A, 208B, or 208C based on frequencies at which datavalues are stored on other partitions of the storage medium 104.According to one example, the first partition 208A and the secondpartition 208B each has storage space to store 100 data values and eachcurrently, stores 50 data values. Further, 10 data values have beenadded to the first partition 208A within the last hour, whereas no datavalue has been added to the second partition 208B has within the lastweek. The allocation manager 204 may determine that at the foregoingfrequencies, the first partition 208A may be completely filled with datavalues in 5 hours, whereas the second partition 208B may not becomesaturated in the near future. As such, the allocation manager 204increases the storage space of the first partition 208A by allocatingsome of the unused storage space of the second partition 208B.Additional descriptions of the allocation manager 204 are provided inthe subsequent paragraphs.

FIG. 3 is a schematic view of a data manager 306A and a first partition208A of the storage medium 104 of the data storage system 102 inaccordance with one embodiment. The data storage system 102 initiallyassigns the data manager 306A to manage a data subset of the dataset andto store data values of the data subset on the first partition 208A ofthe storage medium 104. The data manager 306A includes a set ofoperational values 336 containing information and instructions on whereto store data values belonging to the data subset managed by the datamanager 306A. In the example of FIG. 3, the set of operational values336 includes a partition number of the first partition 208A, start andend track values of the first partition 208A, and start and end sectorvalues of the first partition 208A. The set of operational values 336also includes values indicative of a total storage space of the firstpartition 208A, a size of unused space on the first partition 208A, anoffset of the first partition 208A relative to other adjacentpartitions, locations of data values stored on the first partition 208A,a total number of data values stored on the partition, and offset(s) ofone or more data values stored on the first partition 208A. The set ofthe operational values 336 further includes values indicative of a firstkey (start key) of the set of keys assigned to the data subset, a lastkey (end key) of the set of keys assigned to the data subset, a totalnumber of keys assigned to the data subset, locations of the keysassigned to the data subset, as well as other operational values.

The data manager 306A also includes a set of indicators 338 (flags,timer ticks, counters, as well as other types of indicators thatidentify a status of the data values stored on the first partition 208A)that identify whether the storage space of the first partition 208Ashould be readjusted. In the example of FIG. 3, the set of indicators338 includes a grab flag indicative of a request to increase the storagespace of the first partition 208A and a give flag indicative of arequest to decrease the storage space of the first partition 208A. Aclear zero flag indicates that at least one data value belonging to thedata subset managed by the data manager 306A is stored on the firstpartition 208A, whereas a set zero flag indicates that no data valuebelonging to the data subsect managed by the data manager 306A is storedon the first partition 208A. A set change flag indicates that a datavalue belonging to the data subset has been modified since the last timethe data manager 206A accessed the first partition 208A. In someembodiments, the allocation manager 204 periodically queries the datamanager 306A to obtain the status of one or more flags. For example, theallocation manager 204 may periodically query the data manager 306A todetermine if the zero flag is set. If the allocation manager 204determines that the zero flag has been consistently set after athreshold number of queries, the allocation manager 204 may determinethat the partition 208 is under-utilized and that a portion of thestorage space of the first partition 208A should be allocated to anotherpartition of the storage medium 104. In other embodiments, the datamanager 306A provides the status of one or more flags to the allocationmanager 204 in response to a status update of the one or more flags. Forexample, the data manager 306A provides a status update to theallocation manager 204 whenever the status of the give flag or the takeflag changes from clear to set. The allocation manager 204 thenallocates additional storage space to the first partition 208A uponreceipt of a set take flag. Alternatively, the allocation manager 204allocates a portion of unused storage space of the first partition 208Ato another partition upon receipt of a set give flag from the datamanager 306A.

A timer tick represents a value of a number generated by a numbergenerator 342. In some embodiments, the number generator 342 generates anumerical value within a range of numerical values, where the range isconstant among each number generator used to determine whether to adjustthe storage space of the partitions of the storage medium 104. Further,the value is indicative of whether the storage space of the firstpartition 208A should be readjusted and a priority level for readjustingthe storage space of the first partition 208A. In one of suchembodiments, the number generator 342 generates numerical values between−100 and 100, where a numerical value of 0 represents that the storagespace of the first partition 208A is not saturated or under-utilized.Moreover, a positive numerical value represents that the first partition208A is saturated and that additional storage space should be allocatedto the first partition 208A. Further, a negative numerical valuerepresents that the first partition 208A is under-utilized and thatunused storage space of the first partition 208A should be allocated toother partitions of the storage medium 104. The data manager 306A alongwith other data managers of the data storage system 102 periodicallyprovide the timer tick to the allocation manager 204. When theallocation manager 204 receives multiple timer ticks from multiple datamanagers, the allocation manager 204 assigns a higher priority toincrease the storage space of the first partition if the numerical valueof the timer tick is greater than the numerical values of the otherpartitions. Similarly, the allocation manager 204 assigns a higherpriority to decrease the storage space of the first partition 208A ifthe numerical value of the timer tick is negative and is less than thenumerical values of other partitions.

In other embodiments, the number generator 342 generates a numericalvalue indicative of the probability that the received data value isstored on the first partition 208A. The data manager 306A sets the timertick to the generated numerical value, and provides the timer tick tothe system manager 202. In some embodiments, a copy of the operationalvalues 336 and the set of indicators 338 are also stored on the firstpartition 208A. In further embodiments, the operational values 336 andthe set of indicators 338 may be accessed by the allocation manager 204.

In some embodiments, when the system manager 202 receives a data value,the data manager 306A accesses the operational values 336 then accessesthe first section 242A of the first partition 208A based on theoperational values 336 to determine whether the received data value isstored on the first partition 208A. The data manager 206 also accessesthe second section 244A based on the operational values 336 to determinea key for the data value. The data manager 306A then generates one ormore indications that the received data value is assigned to a datasubset managed by the data manager 306A and that the received data valueis stored on the first partition 208A.

The data manager 306A also includes a set of counters 340. The set ofcounters 340 includes a first counter that counts the total number ofdata values belonging to the data subset managed by the data manager306A that are stored on the first partition 208A. The value of the firstcounter may be increased or decreased when new data values belonging tothe data subset are added to the first partition 208A or when existingdata values belonging to the data subset are deleted from the firstpartition 208A, respectively. In some embodiments, the set of counters340 also includes a second counter that counts the number of times(frequency) that new data values are stored on the first partition 208Awithin a threshold operational duration. In some embodiments, the set ofcounters 340 also includes a third counter that counts the number oftimes data values have been deleted from the first partition 208A withinthe threshold operational duration. In some embodiments, the set ofcounters 340 also includes a fourth counter that counts the number oftimes data values belonging to the data subset managed by the datamanager 306A have been modified. The value of the fourth counter isincreased after a data value is stored on the first partition 208A or ifan existing value is modified. In further embodiments, the data manager306A increases the number of counters of the set of counters 340 if theobtained data value or if the new value for the obtained data value isstored on the first partition 208A and decreases the number of countersof the set of counters 340 if a data value is deleted from the firstpartition 208A.

In some embodiments, the data manager 306A provides the values of theset of counters 340 to the allocation manager 204. In other embodiments,the data manager 306A queries the values of the set of counters 340. Theallocation manager 204 may determine whether the first partition 208A issaturated or is under-utilized based on the counter values indicative ofthe total number of data values stored on the first partition 208A. Theallocation manager 204 may also predict when the first partition 208Amay become saturated or become under-utilized based on the countervalues indicative of the number of times new data values have been addedto the first partition 208A or deleted from the first partition 208Awithin the threshold operational duration.

In some embodiments, the data storage system 102 also includes a mapgenerator (not shown) that generates a density map of the data valuesbased on the counter values of the data manager 306A as well as otherdata managers of the data storage system 102. In further embodiments,the map generator generates a density map of the data values based onthe number of counters of the data manager 306A as well as the number ofcounters of the other data managers of the data storage system 102. Inone of such embodiments, the density map illustrates a distribution ofthe data values stored on the partitions of the storage medium 104. Inanother one of such embodiments, the density map illustrates a frequencyof the data values received by the data storage system 102.

The data manager 306A also includes a buffer 334, where the buffer 334is a storage medium for storing data values before the data values arestored on the first partition 208A. In some embodiments, the buffer 334is a temporary storage medium that is dynamically allocated to hold datavalues during read/write operations described in the followingparagraphs. In other embodiments, the buffer 334 is a persistentcomponent of the data manager 306A. In further embodiments, the buffer334 is an independent component of the data storage system 102 and isshared by multiple data managers. In one of such embodiments, each ofthe multiple data managers stores data values in the buffer 334 whileperforming read and write operations described following paragraphs.

The data manager 306A operates the data reader 330 and the data writer332 to transfer (read/write) data values from the first partition 208Ato the buffer 334 and from the buffer 334 to the first partition 208A,respectively. In some embodiments, the data manager 306A determineswhether a received data value stored on the buffer 334 is stored on thefirst partition 208A. The data manager 306A then operates the datawriter 332 to write the received data value from the buffer 334 to thefirst partition 208A if the data value is not stored on the firstpartition 208A. In further embodiments, the data manager 306A checks ifthe change flag is set to determine if a data value stored on the firstpartition 208A has been modified by the data value received by the datamanager 306A. If the change flag for a data value stored on the firstpartition 208A is set, then the data manager 306A operates the datareader 330 to read the stored data value onto the buffer 334. The datamanager 306A then compares the stored data value with the received datavalue and operates the data writer 332 to write the received data valueonto the first partition 208A to replace the stored data value. Infurther embodiments, the data manager 306A operates the data reader 330to read the data value from the first partition 208A onto the buffer 334and operates the data writer 332 to write the data value to anotherpartition (not shown) of the storage medium 104.

The data manager 306A may add a new data value to the data subsetmanaged by the data manager 306A. In some embodiments, the data manager306A obtains the new data value based on a key assigned to the new datavalue, loads the new data value onto the buffer 334, and writes the newdata value at a location on the first partition 208A based on theoperational values 336. In one of such embodiments, the data manager306A then sets the zero flag to indicate that the new data value isstored on the first partition 208A and sets the change flag to indicatethat the original dataset has been modified.

The data manager 306A may also delete an existing data value from thedata subset managed by the data manager 306A. In some embodiments, thedata manager 306A assesses the set of indicators to determine if thezero flag is set. If the zero flag is set, then no data value belongingto the data subset managed by the data manager 306A is stored on thefirst partition 208A and the data manager 306A returns an indicationthat the delete operation is not performed since there is no data valueto delete from the first partition 208A. In one of such embodiments,where the zero flag is not set, the data manager 306A operates the datareader 330 to load all data values belonging to the data subset onto thebuffer 334, deletes the existing data value, and sets the change flag toindicate that at least one data value belonging to the data subsetmanaged by the data manager 306A has been modified. The data manager306A also sets the zero flag if no additional data value belonging tothe data subset is stored on the first partition after deletion of theexisting data value. The data manager 306A then writes the data valuesto the first partition 208A.

In some embodiments, the data manager 306A may also rearrange datavalues of the data subset that are stored on the first partition 208A.In some embodiments, the data manager 306A accesses the operationalvalues 336 to determine if there are offsets between data values storedon the first partition 208A. In one embodiment, if there are offsetsbetween the data values, the data manager 208A determines if the offsetdata values may be moved to a new location on the first partition toeliminate the offset. If so, then the data manager 306A moves the offsetdata values to the new location. The data manager 306A then updates theoperational values 336 to include the new addresses of the data values.

FIG. 4 is a schematic view of the allocation manager 204 of FIG. 2assigned to the first, second, and third data managers 206A-206C and tothe first, second, and third partitions 208A-208C of the storage medium104 in accordance with one embodiment. Each data manager of the first,second, and third data managers 206A-206C is operable to perform variousoperations described herein to obtain, to store, and to modify datavalues and key values.

As stated herein, the allocation manager 204 may periodically query thefirst, second and third data managers 206A-206C to determine the storagespace of each of the first, second, and third partitions 208A-208C, andto determine whether to adjust the storage space of the first, second,and/or third partitions 208A-208C. In some embodiments, the allocationmanager 204 accesses the operational values and indicators of one ormore data managers 206A-206C to determine the storage space of thefirst, second, and third partitions 208A-208C, location of the first,second, and third partitions, and offset information. The allocationmanager 204 also accesses operational values, indicators, and countersdiscussed herein to determine whether to increase or decrease thestorage space of the of the partitions 208A-208C. In one of suchembodiments, the allocation manager 204 accesses the indicators of eachdata manager 206A-206C to determine whether the give flag or grab flagof the respective data manager are set. In one example, if the grab flagof the first data manager 206A is set and the give flags of the secondand the third data managers 206B and 206C are set, then unused storagespace should be reallocated from the second and third partitions 208Band 208C, which store data subsets managed by the second and third datamanagers 206B and 206C, to the first partition 208A, which stores thedata subset managed by the first data manager 206A. If the allocationmanager 204 determines that multiple data managers have grab or giveflags set, then the allocation manager 204 retrieves one or more timerticks from each data manager 206A-206C. In one of such embodiments, theallocation manager 206A prioritizes the allocation process based thetimer tick values of the first, second, and third data managers206A-206C. As such, if the allocation manager 204 determines that thefirst data manager 206A and another data manager (not shown) both havegrab flags set, and the data manager 206A has a higher timer tick valuerelative to the other data manager, then the allocation manager 204priorities increasing the storage space of the first partition 208A.Alternatively, if the allocation manager 204 determines that the seconddata manager 206B and the third data manager 206C both have give flagsset, and the absolute value of the timer tick of the second data manager206B is less than the absolute value of the timer tick of the third datamanager 206C, then the allocation manager 204 priorities decreasing thestorage space of the third partition 208C.

In another one of such embodiments, the allocation manager 204 accessesthe counter values of the first, second, and third data managers206A-206C to determine the total number of data values stored on each ofthe first, second, and third partitions 208A-208C. In a further one ofsuch embodiments, the allocation manager 204 accesses the counter valuesof the first, second, and third data managers 206A-206C to determine thenumber of times (frequency) new data values have been added to each ofthe first, second, and third partitions 208A-208C, or the number oftimes existing data values have been modified or deleted from each ofthe first, second, and third partitions 208A-208C. The allocationmanager 204 then prioritizes the allocation process based on the countervalues of the first, second, and third data managers 206A-206C.

In some embodiments, the allocation manager 204 prioritizes theallocation process based on counter values indicative of the currentnumber of data values stored on the first, second, and third partitions208A-208C as well as well as counter values indicative of a predictednumber of data values stored on the first, second, and third partitions208A-208C to prioritize the allocation process. In one exampleembodiment, each of the first, second, and third partitions 208A-208Chas storage space to store 100 data values and the allocation manager204 determines from the counter values that the first partition 208Acurrently stores 90 data values, the second partition 208B currentlystores 50 data values, and the third partition 208C currently stores 10data values. In such embodiment, the allocation manager 204 maydetermine that the first partition 208A is saturated and that the thirdpartition 208C is under-utilized. The allocation manager 204 thenallocates unused storage space from the third partition 208C to thefirst partition 208A. However, if the allocation manager 204 alsodetermines from the counter values that no new data value has been addedto the first partition 208A within the last year, 10 data values havebeen removed from the second partition 208B within the last week, andthat all 10 of the data values currently stored on the third partition208C have been added within the last minute, then the allocation manager204 may predict that the third partition may become saturated within thenext 9 minutes and allocate unused storage space from the secondpartition 208B to the third partition 208C.

The allocation manager is also operable to assign multiple data managersto store data values of data subsets belonging to the data managers on asingle partition. In one example, if after an operational duration, thestorage medium 104 does not contain any data value belonging to a subsetmanaged by the second data manager 206B or the third data manager 206C,then the data storage system 102 may determine that the data storagesystem 102 is unlikely to receive data values belonging to the datasubsets managed by the second data manager 206B and the third datamanager 206C, respectively. As such, the allocation manager 204re-assigns the second data manager 206B to the third partition 208C. Theallocation manager 204 may also reallocate some or all of the storagespace of the second partition 208B to another partition of the storagemedium 104.

Similarly, the allocation manager 204 may also reallocate key valuesstored on one partition to a different partition of the storage medium104. The second partition 208B of the foregoing example, stores a set ofkey values assigned to each data value of the data subset managed by thesecond data manager 206B. Once the allocation manager 204 determines toreassign the second data manager 206B to the third partition 208C, theallocation manager 204 may also store the key values of the data subsetmanaged by the second data manager 206B on the third partition 208C. Infurther embodiments, the allocation manager 204 reallocates all of thedata values and key values initially stored on the second partition 208Bto the third partition 208C. In further embodiments, the allocationmanager 204 combines the second and the third partitions 208B and 208Cto form a new partition (not shown) and stores data values and keyspreviously stored on the second and the third partitions 208B and 208Con the new partition.

FIG. 5A is a schematic view of an initial state of the first, second,and third partitions 208A-208C, and the first, second, and third datamanagers 206A-206C of FIG. 4, and a key space 550 containing three setsof keys 551A-551C mapped to data values stored on the first, second, andthird partitions 208A-208C in accordance with one embodiment. The datastorage system 102 initially divides a dataset into a first, a second,and a third data subset, and assigns the first, the second, and thethird data manager 206A-206C to manage the first, the second, and thethird data subset, respectively. The data storage system 102 alsodivides the storage medium 104 approximately evenly into first, second,and third partitions 208A-208C for storing data values belonging to thethree data subsets. A key manager (not shown) of the data storage system102 divides the key space 550 approximately evenly into a first set ofkeys 551A, a second set of keys 551B, and a third set of keys 551C, andassigns the first, second and third sets of keys 551A-551C to the first,second, and third data subset, respectively.

Over time, the data storage system 102 receives more data valuesbelonging to the first data subset relative to the second and the thirddata subsets, thereby causing the first partition 208A to becomesaturated and causing the second and third partitions 208B and 208C tobecome under-utilized. FIG. 5B is a schematic view of the partitions,208A-208C, data managers 206A-206C, and key space of FIG. 5A at time Tafter the initial state in accordance with one embodiment. Theallocation manager 204 performs the operations described herein toallocate unused storage space from the second and third partitions 208Band 208C to the first partition 208A. As such, after time T, the storagespace of the first partition 208A has been increased to store additionaldata values belonging to the first data subset, and the storage spacesof the second and the third partitions 208B and 208C have beencorrespondingly decreased since few data values belonging to the secondor the third data subsets have been stored on the second or the thirdpartition 208B or 208C.

In some embodiments, the allocation manager 204 operates a key manager(not shown) described herein to remap the key space 550 to increase thenumber of keys of the first set of keys and to decrease the number ofkeys in the second and third sets of keys. As illustrated in FIG. 5B, anumber of keys initially assigned to data values belonging to the secondor third data subset have been remapped and reassigned to data valuesbelonging to the first data subset. As the data storage system 102continues to operate, the allocation manager 204 and key managercontinues to dynamically readjust the storage space of the partitionsand remap the key space to data values stored on the partitions of thestorage medium 104.

The data storage system 102 may receive data values belonging toextremely large datasets (big data) or data values having multipleparameters. The data storage system 102 may also be implemented tofacilitate storage of data values belonging to such datasets, FIG. 6 isa schematic view of the data storage system 102 of FIG. 1 havingmultiple layers (multi-layer data storage system) in accordance with oneembodiment. The data storage system 102 includes a system manager 602, astorage medium 104 having eight partitions 208A-208H, a key manager 603,top layer data managers 606A and 606B, intermediate layer data managers616A-616D, and bottom layer data managers 626A-626H. As defined herein,“top,” “intermediary,” “bottom,” “higher,” and “lower” refer to datatransfer hierarchies. The terms “top,” “intermediary,” and “bottom” donot refer to an orientation of the data managers of the data storagesystem 102. Further, data values are transferred from the system manager602 “down” to a top layer data manager, from the top layer data manager“down” to an intermediary layer data manager, and from the intermediarylayer data manager “down” to a bottom layer data manager. Data valuesare transferred from the bottom layer data manager “up” to theintermediary layer data manager, from the intermediary layer datamanager “up” to the top layer data manager, and from the top layer datamanager “top” to the system manager 602. Data values are transferredfrom a “lower” layered data manager “up” to a “higher” layered datamanager and are transferred from the “higher” layered data manager“down” to the “lower” layered data manager.

In some embodiments, each layer of the data storage system 102subdivides a dataset and key values assigned to the dataset into smallerportions that may be easier managed by a data manager. In one exampleembodiment, if a dataset contains every financial transaction within thelast two years, then each of the top layer data managers 606A and 606Bis assigned to handle data values and key values belonging totransactions that occurred within one of the two years. Further, each ofthe intermediary data managers 616A-616D is assigned to handletransactions that occurred within a half year of the two years. Further,each of the bottom layer data managers 626A-626H is assigned to handletransactions that occurred within a quarter of the two years. Additionalintermediary layers (not shown) may be utilized to further subdivide thefinancial transactions to transactions that occurred within a month, aweek, a day, or a different duration of time. The system manager 602,similar to the system manager 202 of FIG. 2, receives data values fromthe external sources 108, 110, 112, and 114 and assigns each receiveddata value to a data subset of the dataset. The key manager 603 mapseach data value of the dataset to a key on a key space, and assigns akey of the key space to each data value of the dataset. The key manager603 also divides the key space into multiple sets of keys and assignsthe sets of keys to the top layer data managers 606A and 606B. The keymanager 603 divides the key space into two sets of keys and assigns afirst set of keys to a first top layer data manager 606A and a secondset of keys to a second top layer data manager 606B. In otherembodiments, the key manager 603 may divide the key space into adifferent number of sets of keys and may assign the sets of keys to adifferent number of top layer data managers. In further embodiments, thekey manager 603 may assign multiple sets of keys of the key space to asingle top layer data manager. In some embodiments, the key manager 603is a subcomponent of the system manager 602.

The top layer data managers 606A and 606B, upon receipt of the first setof keys and the second set of keys, respectively, further divides theset of keys. More particularly, the first top layer data manager 606Adivides the first set of keys into a first subset of keys and a secondsubset of keys, and provides the first subset of keys and the secondsubset of keys to a first intermediary layer data manager 616A and asecond intermediary layer data manager 616B, respectively. Similarly,the second top layer data manager 606B divides the second set of keysinto a third subset of keys and a fourth subset of keys and provides thethird subset of keys and the fourth subset of keys to a thirdintermediary layer data manager 616C and a fourth intermediary layerdata manager 616D, respectively.

The intermediary layer data managers 616A-616D further divide the foursubsets of keys into eight subsets of subsets of keys and provide theeight subsets of subsets of keys to bottom layer data managers626A-626H. In the foregoing financial transactions example, each set ofkeys received by a top layer data manager 606A or 606B contains keysassigned to data values corresponding to financial transactions thatoccurred within one year of the two years. Further, each subset of keysreceived by an intermediary layer data manager 616A, 616B, 616C or 616Dcontains keys is assigned to data values corresponding to financialtransactions that occurred within a half year of the two years. Further,each subset of the subset of keys received by a bottom layer datamanager 626A, 626B, 626C, 616D, 626E, 626F, 626G, or 626H is assigned todata values corresponding to financial transactions that occurred withina quarter of the two years. Although FIG. 6 illustrates one intermediarylayer of data managers, the data storage system 102 may include multiplelayers of data managers. In such embodiments, each intermediary layerdata manager receives a subset of keys from a higher layer data manager,divides the received subset of keys into subsets of the subset of keys,and provides the subsets of the subset of keys to one or more lowerlayer data managers. In further embodiments, the data storage system 102only includes top layer data managers 606A and 606B, and bottom layerdata managers 626A-626H. In such embodiments, each top layer datamanager 606A and 606B provides subsets of keys directly to one or morebottom layer data managers 626A-626H.

Each bottom layer data manager 626A-626H is assigned a data subset ofthe dataset. Further, each bottom layer data manager 626A-626H alsoobtains a subset of keys (subset of subset of keys, subset of subset ofsubset of keys, and additional subsets of subset of the keys.) of thekey space assigned to the data subset. Each bottom layer data manager626A-626H is operable to store a data value of the data subset assignedto the respective bottom layer data manager and corresponding keys on apartition 208A-208H of the storage medium 104 assigned to store datavalues belonging to the respective data subset.

Similar to the first, second, third, and fourth data managers 206A-206Dof FIG. 2, each of the bottom layer data managers 626A-626H is operableto determine whether a data value received by the system manager 202belongs to a subset managed by the respective bottom layer data manager626A, 626B, 626C, 626D, 626E, 626F, 626G, or 626H. In some embodiments,each of the bottom layer data managers 626A-626H calculates aprobability that the data value belongs to a data subset managed by therespective data manager 626A, 626B, 626C, 626D, 626E, 626F, 626G, or626H.

In some embodiments, data values and instructions are transmitted fromthe system manager 602 down each layer of data managers until the datavalues or the instructions are transmitted to one or more bottom layerdata managers 626A-626H and vice versa. For example, each of the bottomlayer data managers 626A-626H provides the calculated probability to adata manager one layer higher than the respective bottom layer datamanager. In some embodiments, the first bottom layer data manager 626Aprovides the probability that a data value obtained by the systemmanager 602 is assigned to a data subset managed by the first bottomlayer data manager 626A to the first intermediary layer data manager616A. The first intermediary layer data manager 616A then transmits theprobability to the first top layer data manager 606A, which in turntransmits the probability to the system manager 602. The system manager602, upon determining that the data value belongs to a data subsetmanaged by first bottom layer data manager 626A, transmits the datavalue to the first top layer data manager 606A. The data value is thentransmitted down each layer data managers until the data value istransmitted to the first bottom layer data manager 626A. In someembodiments, a higher layer data manager is operable to calculate theprobability that the data value should be assigned to or passed to oneof the lower layer data managers communicatively connected to the highlayer data manager. For example, the first top layer data manager 606A,upon receipt of a data value, determines the probability that the datavalue should be assigned to the first intermediary data manager 616A andthe probability that the data value should be assigned to the secondintermediary data manager 616B. The first top layer data manager 606Athen passes the data value to the intermediary data manager 616A or 616Bhaving the highest probability for receiving the data value. Thisprocess is continued at each layer until the data value is passed to thebottom layer data manager having the highest probability for receivingthe data value.

The first bottom layer data manager 626A, upon obtaining the data value,then stores the data value on a first partition 208A. In otherembodiments, data values and instructions are directly transmittedbetween the system manager 602 and the bottom layer data managers626A-626H. Although the embodiment of FIG. 6 illustrates a single systemmanager 602, in other embodiments, the data storage system 102 includesmultiple system managers (not shown) that operate to assign differentdata subsets of the dataset and corresponding keys to different layereddata managers. Further, although FIG. 6 illustrates that each bottomlayer data manager 626A-626H stores data values on a single partition,in some embodiments, the bottom layer data managers 626A-626H may storedata values on multiple partitions. In the foregoing financialtransaction example, the first bottom layer data manager 626A storeseach data value and key, corresponding to a transaction that occurredwithin a first quarter of a first year of the two year period on thefirst partition 208A. In some embodiments, the first bottom layer datamanager 626A may also store data values corresponding to transactionsthat occurred within the first quarter of the first year on otherpartitions (not shown) allocated to store the data values correspondingto financial transactions that occurred within half a year, a year, or adifferent duration of time. In one of such embodiments, the partitions208A-208H are periodically updated to include only the most recent twoyears of transactions. In such embodiment, data values stored on thefirst partition 208A are periodically modified or replaced with datavalues corresponding to more recent financial transactions. However,since the bottom layer data manager 626A also stores a copy of the datavalues on a different partition allocated to store data valuescorresponding to financial transactions occurred within a differentduration of time, the data values are maintained on the data storagesystem 102 even when the partitions 208A-208H are updated.

The data storage system 102 also includes one or more allocationmanagers (not shown). The allocation managers, similar to the allocationmanagers shown in FIGS. 2 and 4, are operable to determine whether toadjust the storage space of one or more of the partitions 208A-208H, andto dynamically readjust the storage space of the one or more partitions208A-208H.

FIG. 7 is a schematic view of the data storage system 102 of FIG. 1having multiple layers of data managers in accordance with anotherembodiment. In some embodiments, data values belonging to approximatelya first half (the first half) of the dataset are analyzed by a firstdata analyzer 705A. A first key manager 703A maps each data value of thefirst half of the dataset to a key of a key space, and assigns a key ofthe key space to each data value of the first half of the dataset.Further, a second data analyzer 705B analyzes data values belonging toapproximately a second half (the second half) of the dataset. A secondkey manager 703B maps each data value of the second half of the datasetto a key of the key space, and assigns a key of the key space to eachdata value of the second half of the dataset.

The first data analyzer 705A provides the first half of keys of the keyspace to a first and a second top layer data manager 706A and 706B. Thefirst top data layer data manager 706A obtains a first set of the firsthalf of keys, divides the first set of the first half of keys into afirst subset and a second subset of the first set of the first half ofkeys, and provides the first subset and the second subset to a first anda third bottom layer data manager 726A and 726C, respectively.Similarly, the second top layer data manager 706B obtains a second setof keys of the first half of keys, divides the second set of keys into afirst subset and a second subset of the second set of keys, and providesthe first subset and the second subset of the second set of keys to asecond bottom layer data manager 726B and a fourth bottom layer datamanager 726D, respectively.

The second data analyzer 705B provides the second half of keys of thekey space to a third and a fourth top layer data manager 706C and 706D.The third top data layer data manager 706C obtains a first set of thesecond half of keys and divides the first set of the second half of keysinto a first subset and a second subset of the first set of the secondhalf of keys, and provides the first subset and the second subset of thefirst set of second half of keys to the first and the second bottomlayer data manager 726A and 726B, respectively. Similarly, the fourthtop layer data manager 706D obtains a second set of keys of the secondhalf of keys, divides the second set of keys of the second half of keysinto a first subset and a second subset of the second set of the secondhalf of keys, and provides the first subset and the second subset of thesecond set of the second half of keys to a third bottom layer datamanager 726C and a fourth bottom layer data manager 726D, respectively.Although the dataset and key space of the foregoing embodiment aredivided to a first half and a second half, the dataset and key space maybe divided into other ratios and managed by a different number of toplayer data managers.

In some embodiments, the first subset of the first set of the first halfof key space and the first subset of the first set of the second half ofkey space combine to include keys of a data subset assigned to the firstbottom layer data manager 726A. Similarly, the first subset of thesecond set of the first half of key space and the second subset of thefirst set of the second half of key space combine to include keys of adata subset assigned to the second bottom layer data manager 726B.Further, the second subset of the first set of the first half of keyspace and the first subset of the second set of the second half of keyspace combine to include keys of a data subset assigned to the thirdbottom layer data manager 726C, and the second subset of the second setof the first half of key space and the second subset of the second setof the second half of key space combine to include keys of a data subsetassigned to the fourth bottom layer data manager 726D.

Each bottom layer data manager 726A-726D stores data values belonging todata subsets assigned to the respective bottom layer data manager andcorresponding subsets of keys on partitions 208A-208D, respectively.Further, similar to the embodiment illustrated in FIG. 6, data valuesand instructions may be transmitted between the system manager 702 andthe bottom layer data managers 726A-726D via one or more top layer datamanagers 706A-706D. For example, the first bottom data manager 726A maytransmit a probability that a key belonging to a first set of the firsthalf of keys of the key space to the first top layer data manager 706A,and may transmit a probability that a key belonging to a first set ofthe second half of keys of the key space to the third top layer datamanager 706C. The system manager 702, may transmit a data value having akey belonging to the first subset of the first half of the key space tothe first bottom layer data manager 726A via the first top layer datamanager 706A, and may transmits a data value having a key belonging tothe first subset of the second half of the key space to the first bottomlayer data manager 726A via the third top layer data manager 706C.

In further embodiments, the first bottom layer data manager 726A isassigned a data subset from the first top layer data manager 706A, adata subset from the third top layer data manager 706C, and two subsetsof keys assigned to the two data subsets. Similarly, the second bottomlayer data manager 726B is assigned a data subset from the second toplayer data manager 706B, a data subset from the third top layer datamanager 706C, and two subsets of keys assigned to the two data subsets.The third bottom layer data manager 726C is assigned a data subset fromthe first top layer data manager 706A, a data subset from the fourth toplayer data manager 706D, and two subsets of keys assigned to the twodata subsets. The fourth bottom layer data manager 726D is assigned adata subset from the second top layer data manager 706B, a data subsetfrom the fourth top layer data manager 706D, and two subsets of keysassigned to the two data subsets.

In further embodiments, data values of the dataset include multipleparameters. For example, a dataset of financial security transactionsincludes a parameter based on transaction type (e.g., stock transaction,bond transaction, options transaction, forex transaction, as well asother types of transactions), a second parameter based on transactionsettlement date, and a third parameter based on a type of entity thatexecuted the financial transaction (individual, corporation, non-profitentity, as well as other entity classifications.) The first dataanalyzer 705A analyzes data values of the dataset for data values basedon the transaction type and the second data analyzer 705B analyzes thedata values of the dataset based on transaction date. The first keymanager 703A maps each data value of the dataset to a first set of keysof the key space and assigns a key of the first set of keys of key spaceto each data value. Similarly, the second key manager 703B maps eachdata value of the dataset to a second set of the key of the space, andassigns a key of the second set of keys of the key space to each datavalue. The first, second, third, and fourth top layer data managers706A-706D divide the keys mapped to the data values and provide the keysto the first, second, third, and fourth bottom layer data managers726A-726D. Data values and instructions may be transmitted from thesystem manager 702 to the bottom layer data managers 726A-726D directlyor through one of the top layer data managers 706A, 706B, 706C, or 706D.

In further embodiments, where data values of the dataset includemultiple parameters, the first data analyzer 705A analyzes data valuesof the dataset for data values sharing a first common parameter, and thesecond data analyzer 705B analyzes the data values of the dataset fordata values sharing a second common parameter. The first key manager703A maps each data value of the dataset having a first common parameterto a key of the key space, and assigns a key of the key space to eachdata value of the dataset having the first common parameter. Similarly,the second key manager 703B maps each data value of the dataset having asecond common parameter to a key of the key space, and assigns a key ofthe key space to each data value of the dataset having the second commonparameter. Further, each of the first, second, third, and fourth toplayer data managers 706A-706D divides the keys mapped to the data valuesand provides the keys to the first, second, third, and fourth bottomlayer data managers 726A-726D. Data values and instructions may betransmitted from the system manager 702 to the bottom layer datamanagers 726A-726D directly or through one of the top layer datamanagers 706A, 706B, 706C, or 706D as disclosed herein.

Although FIG. 7 illustrates two data analyzers 705A and 705B and two keymanagers 703A and 703B, the data storage system 102 may include adifferent number of data analyzers and key managers to analyze datavalues and to assign keys to the data values. In some embodiments, thedata storage system 102 includes a data analyzer that analyzes thecontent of each data value received by the data storage system 102 todetermine whether to accept the received data value from the externalsources 108, 110, 112, and 114. In one of such embodiments, the dataanalyzer is a packet sniffer that analyzes the content of data valuestransmitted from the external sources 108, 110, 112, and 114 prior toproviding the data values to the system manager 202.

Further, although FIG. 7 illustrates four top layer data managers706A-706D, no intermediary layer data managers, and four bottom layerdata managers 726A-726D, the data storage system may include a differentnumber of top layer data managers, intermediary layer data managers, andbottom layer data managers. In some embodiments, the bottom layer datamanager 726A-726D each receives data values from two top layer datamanagers, thereby forming a two dimensional array. In furtherembodiments, the bottom layer data manager 726A-726D may each receivedata values from three top layer data managers, thereby forming a threedimensional array. In further embodiments, the bottom layer data manager726A-726D may each receive data values from four or more top layer datamanagers, thereby forming a multi-dimensional array.

As used in this specification and any claims of this application, theterms “computer”, “server”, “processor”, and “memory” all refer toelectronic or other technological devices. As used in this specificationand any claims of this application, the terms “computer readable medium”and “computer readable media” are entirely restricted to tangible,physical objects that store information in a form that is readable by acomputer. These terms exclude any wireless signals, wired downloadsignals, and any other ephemeral signals.

The above-disclosed embodiments have been presented for purposes ofillustration and to enable one of ordinary skill in the art to practicethe disclosure, but the disclosure is not intended to be exhaustive orlimited to the forms disclosed. Many insubstantial modifications andvariations will be apparent to those of ordinary skill in the artwithout departing from the scope and spirit of the disclosure. Forinstance, although the flowcharts depict a serial process, some of thesteps/processes may be performed in parallel or out of sequence, orcombined into a single step/process. The scope of the claims is intendedto broadly cover the disclosed embodiments and any such modification.

The above disclosed embodiments have been presented for purposes ofillustration and to enable one of ordinary skill in the art to practicethe disclosed embodiments, but is not intended to be exhaustive orlimited to the forms disclosed. Many insubstantial modifications andvariations will be apparent to those of ordinary skill in the artwithout departing from the scope and spirit of the disclosure. Forinstance, although the flowcharts depict a serial process, some of thesteps/blocks may be performed in parallel or out of sequence, orcombined into a single step/block. The scope of the claims is intendedto broadly cover the disclosed embodiments and any such modification.

As used herein, the singular forms “a”, “an” and “the” are intended toinclude the plural forms as well, unless the context clearly indicatesotherwise. It will be further understood that the terms “comprise”and/or “comprising,” when used in this specification and/or the claims,specify the presence of stated features, steps, operations, elements,and/or components, but do not preclude the presence or addition of oneor more other features, steps, operations, elements, components, and/orgroups thereof. In addition, the steps and components described in theabove embodiments and figures are merely illustrative and do not implythat any particular step or component is a requirement of a claimedembodiment.

What is claimed is:
 1. A computer-implemented method for storing data,comprising: receiving a data value of a dataset; assigning a pluralityof keys of a key space to a plurality of data values of the dataset;determining whether to readjust storage space of at least one partitionof a plurality of partitions based on data values stored on theplurality of partitions; and in response to a determination to readjustthe at least one partition, dynamically re-mapping the key space toreadjust a number of keys of the plurality of keys that are assigned todata values stored on the plurality of partitions based on a number ofdata values that are stored on the plurality of partitions.
 2. Thecomputer-implemented method of claim 1, further comprising: determininga frequency at which data values of the dataset are stored on the atleast one partition, wherein determining whether to readjust the storagespace of the at least one partition is based on the frequency at whichdata values of the dataset are stored on the at least one partition. 3.The computer-implemented method of claim 2, further comprisingpredicting whether to readjust the storage space of the at least onepartition based on the frequency at which data values of the dataset arestored on the at least one partition within an operational duration. 4.The computer-implemented method of claim 3, wherein predicting whetherto readjust the storage space of the at least one partition furthercomprises: predicting when a first partition of the plurality ofpartitions becomes saturated; increasing storage space of the firstpartition if the first partition is predicted to become saturated withina first threshold operational duration; and decreasing the storage spaceof the first partition if the first partition is not predicted to becomesaturated within a second threshold operational duration.
 5. Thecomputer-implemented method of claim 3, wherein predicting whether toreadjust the storage space of the at least one partition furthercomprises: predicting when a first partition of the plurality ofpartitions becomes saturated; predicting when a second partition of theplurality of partitions becomes saturated; increasing storage space ofthe first partition if the first partition is predicted to becomesaturated sooner than the second partition; and decreasing the storagespace of the first partition if the second partition is predicted tobecome saturated sooner than the first partition.
 6. Thecomputer-implemented method of claim 1, further comprising: determininga storage capacity of the at least one partition, wherein determiningwhether to readjust the storage space of the at least one partition isbased on the storage capacity of the at least one partition.
 7. Thecomputer-implemented method of claim 1, further comprising: determininga number of data values stored on each partition of the plurality ofpartitions; increasing storage space of a first partition of theplurality of partitions if the number of data values stored on the firstpartition is greater than the number of data values stored on at leastone other partition of the plurality of partitions; and decreasing thestorage space of the first partition if the number of data values storedon the first partition is less than the number of data values stored onat least one other partition of the plurality of partitions.
 8. Thecomputer-implemented method of claim 7, further comprising: receiving arequest to increase the storage space of the first partition;identifying a second partition of the plurality of partitions that isunder-utilized; decreasing storage space of the second partition by afirst value; and increasing the storage space of the first partition bythe first value.
 9. The computer-implemented method of claim 8, furthercomprising: identifying a third partition of the plurality of partitionsthat is under-utilized; decreasing storage space of the third partitionby a second value; and increasing the storage space of the firstpartition by the second value.
 10. The computer-implemented method ofclaim 9, further comprising combining the second partition and the thirdpartition into a new partition.
 11. A computer-implemented method fordynamically balancing storage space, comprising: receiving a data valueof a dataset having a plurality of data values that share a commonparameter; storing the data value on a partition of a plurality ofpartitions of a storage medium based on a value of a key assigned to thedata value, the key being one or a plurality of keys of a key space,each key of the plurality of keys of the key space being assigned to adifferent data value of the dataset; after storing the data value on thepartition, determining whether to readjust at least one partition of aplurality of partitions of the storage medium; and in response to adetermination to readjust the storage space of the at least onepartition, increasing storage space of a first partition of the at leastone partition; decreasing storage space of a second partition of the atleast one partition, wherein at least a portion of the storage space ofthe second partition that is decreased is allocated to the firstpartition; and re-mapping the key space to readjust a number of keys ofthe plurality of keys that are assigned to data values stored on theplurality of partitions based on a number of data values that are storedon the plurality of partitions.
 12. The computer-implemented method ofclaim 11, further comprising: accessing one or more indicators ofstorage of data values of the dataset, wherein determining whether toreadjust the at least one partition is based on the one or moreindicators of storage of data values of the dataset.
 13. Thecomputer-implemented method of claim 11, further comprising: determininga frequency at which data values of the dataset are stored on the atleast one partition, wherein determining whether to readjust the storagespace of the at least one partition is based on the frequency at whichdata values of the dataset are stored on the at least one partition. 14.The computer-implemented method of claim 11, wherein in response to adetermination to readjust the storage space of the at least onepartition, the method further comprising: increasing a value of a firstcounter of a plurality of counters, the first counter being associatedwith a number of data values of the dataset that are stored on the firstpartition; and decreasing a value of a second counter of the pluralityof counters, the second counter being associated with a number of datavalues of the dataset that are stored on the second partition.
 15. Thecomputer-implemented method of claim 11, further comprising generating adensity map indicative of a frequency of data values of the datasetstored on the plurality of partitions.
 16. A computer-implemented methodfor mapping keys of a key space, comprising: assigning a plurality ofkeys of a key space to a plurality of data values of a dataset, each keyof the plurality of keys being an identifier of a corresponding datavalue, and each key of the plurality of keys of the key space beingassigned to a different data value of the dataset; dividing theplurality of keys into a plurality of set of keys, each set of keysbeing initially assigned to a partition of a plurality of partitions;periodically determining if storage space of at least one partition ofthe plurality of partitions has been readjusted; and in response to adetermination that the storage space of the at least one partition hasbeen readjusted, re-mapping the key space to readjust a number of keysof the plurality of keys that are assigned to data values stored on theplurality of partitions based on a number of data values that are storedon the plurality of partitions.
 17. The computer-implemented method ofclaim 16, further comprising: storing the plurality of keys of the keyspace on the plurality of partitions; and in response to receiving afirst data value of the plurality of data values that is associated witha first key of the key space, determining a partition of the pluralityof partitions to store the first data value based on a partition of theplurality of partitions that stores the first key of the key space. 18.The computer-implemented method of claim 16, wherein re-mapping the keyspace comprises: determining if storage space of a first partition ofthe at least one partition has increased; in response to a determinationthat the storage space of the first partition has increased, increasinga number of keys assigned to data values stored on a first partition;determining storage space of a second partition of the at least onepartition has decreased; and in response to a determination that thestorage space of the second partition has decreased, decreasing a numberof keys assigned to data values stored on the second partition.
 19. Thecomputer-implemented method of claim 16, wherein re-mapping the keyspace comprises: predicting an increase to storage space of a firstpartition of the at least one partition within a first operationalduration; increasing a number of keys assigned to data values stored ona first partition in response to predicting that the storage space ofthe first partition will increase within the first operational duration;predicting a decrease to storage space of a second partition of the atleast one partition within a second operational duration; and decreasinga number of keys assigned to data values stored on the second partitionin response to predicting that the storage space of the second partitionwill decrease within the second operational duration.
 20. Thecomputer-implemented method of claim 19, further comprising: determininga frequency at which data values are stored on the first partition,wherein predicting the increase to the storage space of the firstpartition is based on the frequency at which data values are stored onthe first partition; and determining a frequency at which data valuesare stored on the second partition, wherein predicting the decrease tothe storage space of the second partition is based on the frequency atwhich data values are stored on the second partition.